Repository navigation
[UR][CI] Add unified test result reporting for UR tests - #22909
Conversation
059d872 to
074c6b1
Compare
074c6b1 to
982c30e
Compare
Introduce common tooling for collecting and reporting results from UR conformance and adapter-specific test executions. The implementation: - provides a common execution and reporting path for UR test suites, - collects detailed test statuses and execution statistics, - parses LIT output and JUnit XML to obtain test-level information, - generates human-readable console output and GitHub Step Summary, - preserves full execution logs and XML results as CI artifacts, - separates test execution, result parsing, and summary generation to support future consumers of test result data. This is the first implementation step towards a broader test management and test health monitoring system. Database integration, historical analysis, and automated PR triage are outside the scope of this change.
|
failing test is related with known issue #22858 |
There was a problem hiding this comment.
Note: this should be enough on GitHub, but we could consider copying these artifacts and storing them on a server for longer.
rbanka1
left a comment
There was a problem hiding this comment.
there are also a lot of unnecessary comments, I think most of them could be deleted
…date test type and filter constants
Clarify the distinction between common reporting options (what test categories to show) and execution-specific options (how to format output for CI vs standalone builds).
New architecture: - Parser layer: produces ParsedLogData and ParsedXMLData observations - Reconciliation layer: combines observations into TestRunResult - Summary generator: consumes TestRunResult with group_by_status()
This change introduces common test result collection and reporting for Unified Runtime conformance and adapter-specific CI tests. Compared to the initial version, the implementation has been updated based on review feedback to: - keep LIT test statuses such as SKIPPED and UNSUPPORTED distinct, - reconcile LIT and JUnit XML results without losing LIT-specific status information, - separate test execution, parsing, reconciliation, and presentation responsibilities, - simplify the internal API and remove redundant wrappers and helpers, - keep CI reporting options separate from execution-specific LIT options. Focused regression tests were added for the non-trivial result mapping and reconciliation behavior identified during review.
sarnex
left a comment
There was a problem hiding this comment.
only took a quick look at the yml changes, lgtm
There was a problem hiding this comment.
it's not clear to me what WORKFLOW_URL is for
There was a problem hiding this comment.
WORKFLOW_URL is a link to the current workflow run, built from github.server_url, github.repository, and github.run_id. It's printed after the summary to provide a direct way to access the full logs and XML artifacts for that run.
|
@intel/llvm-gatekeepers please consider merging |
|
@intel/llvm-gatekeepers please consider merging |
Introduce common tooling for collecting and reporting results from UR conformance and adapter-specific test executions.
The implementation:
This is the first implementation step towards a broader test management and test health monitoring system. Database integration, historical analysis, and automated PR triage are outside the scope of this change.